Method, system and program product for imposing policy modification constraints

ABSTRACT

Under the present invention meta data specifying modification constraints for one or more of the attributes of an (operational) policy is generated/provided. Thereafter, the meta data is associated with the policy so that the constraints specified by the meta data can govern the modification of the policy. Under the present invention there are at least two ways of associating the meta data with a policy. In one embodiment, the meta data is embodied as a meta policy that can be associated with one or more (operational) policies. In another embodiment, the meta data is inserted into individual policies as additional attributes.

BACKGROUND OF THE INVENTION

1. Field of the Invention

In general, the present invention relates to a method, system andprogram product for imposing policy modification constraints.Specifically, the present invention provides a more effective way tocontrol the modification of operational policies for computerinfrastructures.

2. Related Art

As the use of computer infrastructures becomes more pervasive, there isa growing need to implement policies governing theiroperation/performance. For example, a given infrastructure might have acollection of servers, clients, databases, etc. In such a case, there isa need to ensure optimal operation of the computer infrastructure. Forexample, there might be a need to provide load balancing among theservers so that one server does not become overloaded. To this extent, acertain policy might require that workload be shifted to a second serverwhen the CPU consumption of a first server reaches a certain threshold.In many cases, a typical policy has at least four attributes, namely,scope, precondition, decision and business value. The scope attributegenerally specifies the intended target of the policy. That is, thescope specifies the element of the computer infrastructure (e.g.,server, database, etc.) to which the policy is to be applied. Theprecondition attribute specifies when the policy is to be applied. Forexample, a policy might be applied when CPU consumption reaches acertain threshold, when recovery time for a system becomes too high,etc. The decision attribute specifies an action to be taken if theprecondition occurs. For example, if the precondition attributesspecifies a CPU consumption of 60% for a particular server, the decisionattribute could require shifting workload to a different server when the60% is reached or exceeded. Lastly, the business value attributespecifies a business value for the policy. This allows a priority to bedetermined when more than one policies are applicable.

Once a policy has been established, it can be implemented autonomicallyusing one or more autonomic managers. However, one issue that ariseswith policies is the modification thereof. Specifically, there is oftenthe need to modify a given policy in light of changes to the computerinfrastructure. For example, one policy might state that a minimum ofthree servers needs to be operational within the infrastructure at alltimes. If the minimum number of operational servers is not met, thecorrective action could be to reduce server recovery time from 10minutes to 5 minutes. Accordingly, modification of the policy callingfor the reduction in recovery time to 5 minutes is needed.

To date, policies are largely modified manually by an administrator orby autonomic managers controlling the system. Neither option ispreferred since different administrators or autonomic managers couldhave a different knowledge of the true constraints of theinfrastructure. Moreover, the administrators or autonomic managers wouldmake such changes without full knowledge of valid ranges for the policy.For example, assume under the above scenario that a recovery time ofless than 7.5 minutes is not feasible. The administrator would have toknow this or risk further degradation of the system.

In view of the foregoing, there exists a need for a method, system andprogram product for imposing policy modification constraints.Specifically, a need exists for a system that allows policies to beassociated with any modification constraints corresponding thereto.

SUMMARY OF THE INVENTION

In general, the present invention provides a method, system and programproduct for imposing policy modification constraints. Specifically,under the present invention meta data specifying modificationconstraints for one or more of the attributes of an (operational) policyis generated/provided. Thereafter, the meta data is associated with thepolicy so that the constraints specified by the meta data can govern themodification of the policy. Under the present invention there are atleast two ways of associating the meta data with a policy. In oneembodiment, the meta data is embodied as a meta policy that can beassociated with one or more (operational) policies. In anotherembodiment, the meta data is inserted into individual policies asadditional attributes.

A first aspect of the present invention provides a method for imposingpolicy modification constraints, comprising: providing a policypertaining to operational performance of a computer infrastructure,wherein the policy comprises a set of the attributes; and associatingmeta data with the policy, wherein the meta data specifies at least onemodification constraint governing modification of at least one of theset of attributes.

A second aspect of the present invention provides a computer-implementedmethod for imposing policy modification constraints, comprising:providing a policy pertaining to operational performance of a computerinfrastructure, wherein the policy comprises at least one of attributesof scope, precondition, decision and business value; generating metadata that specifies at least one modification constraint governingmodification of at least one of the attributes; and associating metadata with the policy, wherein the meta data specifies at least onemodification constraint governing modification of at least one of theset of attributes.

A third aspect of the present invention provides a system for imposingpolicy modification constraints, comprising: a meta data generationsystem for generating meta data specifying at least one modificationconstraint governing modification of at least one of a set of attributespresent in a policy pertaining to operation of a computerinfrastructure; and an association system for associating the meta datawith the policy.

A fourth aspect of the present invention provides a program productstored on a recordable medium for imposing policy modificationconstraints, which when executed, comprises: program code for generatingmeta data specifying at least one modification constraint governingmodification of at least one of a set of attributes present in a policypertaining to operation of a computer infrastructure; and program codefor associating the meta data with the policy.

Therefore, the present invention provides a method, system and programproduct for imposing policy modification constraints.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readilyunderstood from the following detailed description of the variousaspects of the invention taken in conjunction with the accompanyingdrawings in which:

FIG. 1 depicts an illustrative technique for implementing a policy.

FIG. 2 depicts an illustrative scenario in which a policy is modified.

FIG. 3 depicts an illustrative system for imposing policy modificationconstraints according to the present invention.

It is noted that the drawings of the invention are not necessarily toscale. The drawings are merely schematic representations, not intendedto portray specific parameters of the invention. The drawings areintended to depict only typical embodiments of the invention, andtherefore should not be considered as limiting the scope of theinvention. In the drawings, like numbering represents like elements.

DETAILED DESCRIPTION OF THE DRAWINGS

As indicated above, the present invention provides a method, system andprogram product for imposing policy modification constraints.Specifically, under the present invention meta data specifyingmodification constraints for one or more of the attributes of an(operational) policy is generated/provided. Thereafter, the meta data isassociated with the policy so that the constraints specified by the metadata can govern the modification of the policy. Under the presentinvention there are at least two ways of associating the meta data witha policy. In one embodiment, the meta data is embodied as a meta policythat can be associated with one or more (operational) policies. Inanother embodiment, the meta data is inserted into individual policiesas additional attributes.

As used herein, the term “policy” is intended to refer to an operationalpolicy or a set of rules/guidelines pertaining to the operation of acomputer infrastructure. Under the present invention, the preciseconfiguration of the computer infrastructure is not intended to belimiting. As known, a computer infrastructure can comprise anyconfiguration of computer hardware and/or software such as servers,clients, databases, routers, etc.

As also indicated above, a policy under the present invention will havea set (e.g., one or more) of attributes. In a typical embodiment, eachpolicy will have four attributes. Such attributes generally include: (1)scope; (2) precondition; (3) decision; and (4) business value (althoughsome embodiments may lack one or more attribute). The scope attributespecifies the intended target of the policy. That is, the scopespecifies the element of the computer infrastructure (e.g., server,database, application component, etc.) to which the policy is to beapplied. The precondition attribute specifies when the policy is to beapplied. For example, the policy might be applicable when CPUconsumption of the element specified in the scope reaches a certainthreshold, when recovery time for a system becomes too high, etc. Thedecision attribute specifies a specific action to be taken if theprecondition occurs. For example, if the precondition is a CPUconsumption of 60% for a server, the decision attribute could requireshifting workload to a different server. Lastly, the business valueattribute specifies a business value for the policy. This allows apriority to be determined when more than one policies are applicable.

Referring now to FIG. 1, an illustrative diagram 10 showing theautonomic implementation of a policy under the present invention isshown. As depicted, a policy could be implemented by multiple autonomicmanagers 12A-B and resource manager 14. Autonomic manager 12A is asolution level autonomic manager that accepts higher level businessgoals, translates business policies into goals and objectives for theresource it is managing, and pushes the goals down onto its managedelements. Autonomic Manager 12B is a touchpoint level autonomic managerthat accepts the goals from autonomic manager 12A, translates the goalsinto effectors to be pressed, pushes down onto the effectors, andmeasures the goals using sensors. Resource manager 14 will accept thedecisions from autonomic manager 12B and manage the resources of thecomputer infrastructure accordingly. Although not shown, an individualsuch as an administrator could push the policy down.

In general, policies often require modification to improve the operationof the computer infrastructure. For example, it could be the case that arecovery time specified within a policy is too long and needs to bereduced. FIG. 2 demonstrates this scenario in greater detail.Specifically, FIG. 2 shows a computer infrastructure 20 (or part of one)comprising servers 22 and storage devices 24. FIG. 2 also shows variousautonomic systems such as a workload manager 26, a provisioning system28, a server recovery manager 30 and a server backup manager 32. Also,computer infrastructure 20 has a requirement 34 that between 3 and 10servers should be operational at any one time. Assume in this examplethat maintaining the minimum number of servers in operation is afunction of recovery time of storage devices 34, as indicated in policy38. Further, assume that an error message 36 has been generated becausethe server requirement has been missed (e.g., only 2 servers areoperational).

In this scenario, an administrator or other personnel could attempt tomodify policy 38 to reduce the recovery time from 10 minutes to 5minutes. Unfortunately, the administrator would have to know whether thenew recovery time of 5 minutes is feasible. Given the quantity ofpolicies a single infrastructure could have, requiring the administratorto know the modification constraints, or be able to reference theconstraints, is highly inefficient. The present invention provides amore effective way to impose modification constraints on policies.

Specifically, referring to FIG. 3, a system 50 for imposing modificationconstraints on policies 72 is depicted. As shown, system 50 includes acomputer system 52, that generally comprises central processing unit(CPU) 54, memory 56, bus 58, input/output (I/O) interfaces 60, externaldevices/resources 62 and storage unit 64. CPU 54 may comprise a singleprocessing unit, or be distributed across one or more processing unitsin one or more locations, e.g., on a client and server. Memory 56 maycomprise any known type of data storage and/or transmission media,including magnetic media, optical media, random access memory (RAM),read-only memory (ROM), a data cache, etc. Moreover, similar to CPU 54,memory 56 may reside at a single physical location, comprising one ormore types of data storage, or be distributed across a plurality ofphysical systems in various forms.

I/O interfaces 60 may comprise any system for exchanging informationto/from an external source. External devices/resources 62 may compriseany known type of external device, including speakers, a CRT, LCDscreen, handheld device, keyboard, mouse, voice recognition system,speech output system, printer, monitor/display, facsimile, pager, etc.Bus 58 provides a communication link between each of the components incomputer system 12 and likewise may comprise any known type oftransmission link, including electrical, optical, wireless, etc.

Storage unit 64 can be any system (e.g., database) capable of providingstorage for information under the present invention. Such informationcould include, for example, a policies, meta data, meta policies, etc.As such, storage unit 64 could include one or more storage devices, suchas a magnetic disk drive or an optical disk drive. In anotherembodiment, storage unit 64 includes data distributed across, forexample, a local area network (LAN), wide area network (WAN) or astorage area network (SAN) (not shown). Although not shown, additionalcomponents, such as cache memory, communication systems, systemsoftware, etc., may be incorporated into computer system 52.

It should be understood that the teachings described herein could beimplemented on a stand-alone computer system 52 as shown in FIG. 1, orover a network in a client-server environment. In the case of thelatter, the client and server could communicate over any type of networksuch as the Internet, a local area network (LAN), a wide area network(WAN), a virtual private network (VPN), etc. As such, communicationbetween the client and server could occur via a direct hardwiredconnection (e.g., serial port), or via an addressable connection thatmay utilize any combination of wireline and/or wireless transmissionmethods. Moreover, conventional network connectivity, such as TokenRing, Ethernet, WiFi or other conventional communications standardscould be used. Still yet, connectivity could be provided by conventionalTCP/IP sockets-based protocol. In this instance, the client couldutilize an Internet service provider to establish connectivity to theserver.

Regardless, shown in memory 56 is constraint system 66, which includesmeta data generation system 68 and association system 70. Under thepresent invention, modification constraints will be imposed on one ormore policies 72 by associating meta data corresponding to themodification constraints with the one or more policies 72. For example,assume that administrator 74 wishes to impose a modification constrainton a specific policy such as policy 38 of FIG. 2. Specifically, assumethat administrator wishes to impose the modification constraint thatwill prevent the recovery time stated in the policy from being reducedbelow 7.5 minutes. Under the present invention, administrator 74 willuse meta data generation system 68 to generate meta data 76 specifyingthe modification constraint. It should be understood, that meta data 76can be generated to specify any quantity of modification constraints. Asingle modification constraint is discussed herein for illustrativepurposes only. In any event, in a preferred embodiment, the meta data 76is embodied by meta data generation system 68 as a meta policy 78 thatcan be associated with the policy as a whole by association system 70.This allows multiple policies 72 to be associated with the modificationconstraint(s) specified in meta policy 78. Specifically, when embodiedas a meta policy 78, the modification constraints can be made applicableto classes or hierarchies of policies. For example, meta policy 78(i.e., the modification constraint therein) could be made applicable toall policies concerning “servers.”

In another embodiment, the meta data 76 is not embodied as a metapolicy, rather is left as meta data 76. In this case, the meta dataspecifying the modification constraint can be inserted into theapplicable policies as an additional attribute. For example if meta data76 specifies one modification constraint, it will be inserted (viaassociation system 70) into each individual the policy with whichadministrator 74 wishes it to be associated as a fifth attribute.Similarly, if meta data 76 specified two modification constraints, theywould be inserted into each policy as the fifth and sixth attributes.Regardless, once the meta data has been associated with the policy(e.g., as meta policy 78 or as plain meta data 76), the associated pair80 can be exported for use. If someone later attempts to modify thepolicy contrary to the modification constraint(s) associated therewith,an error message can be generated. For example, if someone laterattempts to reduce the recover time set forth in policy 38 below 7.5minutes, the attempted modification would not be permitted.

It should be understood that the present invention can be realized inhardware, software, or a combination of hardware and software. Any kindof computer system(s)—or other apparatus adapted for carrying out themethods described herein—is suited. A typical combination of hardwareand software could be a general purpose computer system with a computerprogram that, when loaded and executed, carries out the respectivemethods described herein. Alternatively, a specific use computer,containing specialized hardware for carrying out one or more of thefunctional tasks of the invention, could be utilized. The presentinvention can also be embedded in a computer program product, whichcomprises all the respective features enabling the implementation of themethods described herein, and which—when loaded in a computer system—isable to carry out these methods. Computer program, software program,program, or software, in the present context mean any expression, in anylanguage, code or notation, of a set of instructions intended to cause asystem having an information processing capability to perform aparticular function either directly or after either or both of thefollowing: (a) conversion to another language, code or notation; and/or(b) reproduction in a different material form.

The foregoing description of the preferred embodiments of this inventionhas been presented for purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed, and obviously, many modifications and variations arepossible. Such modifications and variations that may be apparent to aperson skilled in the art are intended to be included within the scopeof this invention as defined by the accompanying claims. For example,the illustrative representation of constraint system 66 shown in FIG. 3is not intended to be limiting. That is, the functions of the presentinvention described herein could be represented by a differentconfiguration of systems.

1. A method for imposing policy modification constraints, comprising: providing a policy pertaining to operational performance of a computer infrastructure, wherein the policy comprises a set of the attributes; and associating meta data with the policy, wherein the meta data specifies at least one modification constraint governing modification of at least one of the set of attributes.
 2. The method of claim 1, wherein the associating step comprises inserting the at least one modification constraint into the policy as at least one an additional attribute.
 3. The method of claim 1, wherein the meta data is embodied as a meta policy, and wherein the associating step comprises associating the meta policy with the policy.
 4. The method of claim 1, wherein the set of attributes comprises the attributes of scope, precondition, decision and business value.
 5. The method of claim 4, wherein the attribute of scope specifies an element of the computer infrastructure that is subject to the policy.
 6. The method of claim 4, wherein the attribute of precondition specifies when the policy is to be applied to the computer infrastructure.
 7. The method of claim 4, wherein the attribute of decision specifies an action to be taken if the attribute of precondition occurs.
 8. The method of claim 4, wherein the attribute of business value specifies a business value of the policy.
 9. A computer-implemented method for imposing policy modification constraints, comprising: providing a policy pertaining to operational performance of a computer infrastructure, wherein the policy comprises at least one of attributes of scope, precondition, decision and business value; generating meta data that specifies at least one modification constraint governing modification of at least one of the attributes; and associating meta data with the policy, wherein the meta data specifies at least one modification constraint governing modification of at least one of the set of attributes.
 10. The method of claim 9, wherein the associating step comprises inserting the at least one modification constraint into the policy as at least one an additional attribute.
 11. The method of claim 9, wherein the meta data is embodied as a meta policy, and wherein the associating step comprises associating the meta policy with the policy.
 12. The method of claim 9, wherein the attribute of scope specifies an element of the computer infrastructure that is subject to the policy.
 13. The method of claim 9, wherein the attribute of precondition specifies when the policy is to be applied to the computer infrastructure.
 14. The method of claim 9, wherein the attribute of decision specifies an action to be taken if the attribute of precondition occurs.
 15. The method of claim 9, wherein the attribute of business value specifies a business value of the policy.
 16. A system for imposing policy modification constraints, comprising: a meta data generation system for generating meta data specifying at least one modification constraint governing modification of at least one of a set of attributes present in a policy pertaining to operation of a computer infrastructure; and an association system for associating the meta data with the policy.
 17. The system of claim 16, wherein the association system inserts the at least one modification constraint into the policy as at least one an additional attribute.
 18. The system of claim 16, wherein the meta data is embodied as a meta policy generated by the meta data generation system, and wherein the association system associates the meta policy with the policy.
 19. The system of claim 16, wherein the set of attributes comprises the attributes of scope, precondition, decision and business value.
 20. The system of claim 19, wherein the attribute of scope specifies an element of the computer infrastructure that is subject to the policy.
 21. The system of claim 19, wherein the attribute of precondition specifies when the policy is to be applied to the computer infrastructure.
 22. The system of claim 19, wherein the attribute of decision specifies an action to be taken if the attribute of precondition occurs.
 23. The system of claim 19, wherein the attribute of business value specifies a business value of the policy.
 24. A program product stored on a recordable medium for imposing policy modification constraints, which when executed, comprises: program code for generating meta data specifying at least one modification constraint governing modification of at least one of a set of attributes present in a policy pertaining to operation of a computer infrastructure; and program code for associating the meta data with the policy.
 25. The program product of claim 16, wherein the program code for associating inserts the at least one modification constraint into the policy as at least one an additional attribute.
 26. The program product of claim 16, wherein the meta data is embodied as a meta policy generated by the program code for generating, and wherein the program code for associating associates the meta policy with the policy.
 27. The program product of claim 16, wherein the set of attributes comprises the attributes of scope, precondition, decision and business value.
 28. The program product of claim 19, wherein the attribute of scope specifies an element of the computer infrastructure that is subject to the policy.
 29. The program product of claim 19, wherein the attribute of precondition specifies when the policy is to be applied to the computer infrastructure.
 30. The program product of claim 19, wherein the attribute of decision specifies an action to be taken if the attribute of precondition occurs.
 31. The program product of claim 19, wherein the attribute of business value specifies a business value of the policy. 